# 100% SIDE Fair Launch

## Details of $SIDE 100% Fair Launch

**Total Supply:** 1 billion $SIDE

**Valuation:** $300K

**Campaign Date:** 00:00:00 (UTC) December 27, 2023 - 23:59:59 (UTC) January 20, 2024

**Total period:** 600 hours

### Token Distribution

<figure><img src="https://t5n2wbylx8n.sg.larksuite.com/space/api/box/stream/download/asynccode/?code=MDU3Y2NlM2UyMTVjZjdhMzMxMDI0ZTU1ZGFkNjQzZDBfd3BjODhaMzkwdm5jMDVGcVFWcWxMZjNrU3lnWkdhSFpfVG9rZW46WjhXOWIwWXk1b2djT1B4akxPMWwwR3dzZ0NnXzE3MDM5MTI5ODg6MTcwMzkxNjU4OF9WNA" alt=""><figcaption></figcaption></figure>

### Community - 20% SIDE

* 1% Participants in Zealy activities
  * July 17, 2023 - January 20, 2024
* 2% Lumoz loyal points holders
  * Allocation based on Lumoz points data from the ZKF community airdrop event.
* 7% $ZKF stakers
  * January 14, 2024 - January 20, 2024
  * A snapshot of [ZKF stake points](https://docs.zkfair.io/economic-model/stake-zkf#stake-points) will be taken everyday
  * Airdrop will be distributed everyday based on the percentage of[ ZKF stake points](https://docs.zkfair.io/economic-model/stake-zkf#stake-points).
* 10% Sideswap protocol contributors

### Sideswap liquidity providers - 40% SIDE

<mark style="color:orange;">**Liquidity Campaign Start Date:**</mark> - 00:00:00 (UTC) December 27, 2023

<mark style="color:orange;">**Liquidity Campaign End Date:**</mark> - 23:59:59 (UTC) January 20, 2024

* **Supported LP token pair**
  * ZKF/USDC
  * WBTC/USDC
  * WBTC/USDT
  * ETH/USDC
  * ETH/USDT
  * USDC/USDT
  * WBTC/ETH
* Distribute 40% of SIDE over 600 hours, allocating 666,666.6666 SIDE per hour.
* Conduct hourly random snapshots of the value of all Sideswap LP tokens and the value of all LP tokens held by users, distributing rewards once per hour.
  * Estimated SIDE = your LP tokens value / total LP tokens value \* SIDE distributed

Example:

| Period                     | Snapshot of total LP tokens value | Snapshot of Bob's LP tokens value | Estimated SIDE                        | Total estimated SIDE for Bob               |
| -------------------------- | --------------------------------- | --------------------------------- | ------------------------------------- | ------------------------------------------ |
| Random time of first hour  | $ 100000                          | $ 1000                            | 6666.6666 (1000/100000\*666666.6666)  | 6666.6666                                  |
| Random time of second hour | $ 180000                          | $ 100                             | 370.3703 (100/180000\*666666.6666)    | 667037.0369 (6666.6666+370.3703)           |
| Random time of third hour  | $ 120000                          | $ 2000                            | 11111.1111 (2000/120000\*666666.6666) | 678148.148 (11111.1111+6666.6666+370.3703) |

#### What's More?

***In addition to receiving a 40% SIDE airdrop, LP providers are also eligible for trade fees*****.**

### Sideswap traders - 40% SIDE

<mark style="color:orange;">**Trading Campaign Start Date:**</mark> 00:00:00 (UTC) January 10, 2024

<mark style="color:orange;">**Trading Campaign End Date:**</mark> - Once the trade fees hit $120,000

* **Total Airdropped SIDE tokens:** 400 million.
* **Total Trade fees:** $120,000.
* Tokens are distributed based on trade fee contributions of all users in this campaign.

{% hint style="warning" %} <mark style="color:orange;">**Once the trade fees hit $120,000, the promotion will conclude, and any subsequent fees will not be considered.**</mark>
{% endhint %}

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sideswap-1.gitbook.io/sideswap/tokenomics/100-side-fair-launch.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.